Skip to content

Conversation

SarahSoutoul
Copy link
Contributor

@SarahSoutoul SarahSoutoul commented Oct 7, 2025

🔎 Previews:

What does this solve?

This PR follows user feedback regarding being confused on how to setup different routes for public and private content in a React Router app, after being in the Declarative mode guide. The solution was to change the sidebar name from Reading user data to Protect content and access user data, to make it more clear to users what type of guide it is. We also wanted to link that guide at the end of the Declarative mode guide as a next step.

What changed?

  • Updated sidebar label for "reading user data" guide
  • Linked the guide at end of declarative mode guide

Important note: Noticed that for other SDKs, the title remains "Read session and user data in your X app with Clerk" (for e.g., Next.js, Tanstack etc). See screenshot below. Do we want to change the titles of those too to be in accordance with the sidebar title?

Checklist

  • I have clicked on "Files changed" and performed a thorough self-review
  • All existing checks pass

Copy link

vercel bot commented Oct 7, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
clerk-docs Ready Ready Preview Oct 8, 2025 8:24pm

@SarahSoutoul SarahSoutoul marked this pull request as draft October 7, 2025 18:33
@SarahSoutoul SarahSoutoul changed the title Refactor the reading user data naming Update sidebar label for "reading user data" guide + linked in Declarative mode react router guide Oct 7, 2025
@SarahSoutoul SarahSoutoul self-assigned this Oct 7, 2025
Copy link
Member

@alexisintech alexisintech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I'd say we can rename all the pages to "Protect content and read user data". "Read" instead of "access" just because the URL is /reading so lets keep read in the title somehow. Plus if you think about CRUD, users should be familiar with what Read means.

for each guide, lets have the metadata title "Read session and user data in your app with Clerk"
metadata titles can be set in the frontmatter with the metadata property

let me know what you think about this direction👂

@SarahSoutoul
Copy link
Contributor Author

SarahSoutoul commented Oct 8, 2025

yeah I'd say we can rename all the pages to "Protect content and read user data". "Read" instead of "access" just because the URL is /reading so lets keep read in the title somehow. Plus if you think about CRUD, users should be familiar with what Read means.

for each guide, lets have the metadata title "Read session and user data in your app with Clerk" metadata titles can be set in the frontmatter with the metadata property

let me know what you think about this direction👂

Here are the changes: Changes post feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants